I'm using ModuleProperties to get such things as last modified time of a module, figuring it would be a lot faster than opening the module. However, I notice that older modules take inordinately long times; in my test cases 7.5secs compared to .18secs for the comperably recently imported module. I notice baselining doesn't help. I notice removing OLE diagrams doesn't help. Anybody got ideas here? perhaps there is something I can do to the database to speed things up. -Louie llandale - Thu Feb 13 14:31:25 EST 2014 |
Re: ModuleProperties Woes Louie, I have no idea what might be going on, but a useful data point might be to take one of your worst performing modules, copy it and see if the copy is any better. Then archive it and see if the restored version is any better. If there is a difference then it is something about the storage within the database rather than the content. From what you have said, I would expect the copy and the restored version to be better. This doesn't directly get you any closer to an answer, but might give someone else more clues. Are your older modules migrated from an earlier version? Can you see a cutoff point where performance improves, or is it a nice (or not so nice) curve? Hazel |
Re: ModuleProperties Woes HazelWoodcock - Thu Feb 13 14:43:24 EST 2014 Louie, I have no idea what might be going on, but a useful data point might be to take one of your worst performing modules, copy it and see if the copy is any better. Then archive it and see if the restored version is any better. If there is a difference then it is something about the storage within the database rather than the content. From what you have said, I would expect the copy and the restored version to be better. This doesn't directly get you any closer to an answer, but might give someone else more clues. Are your older modules migrated from an earlier version? Can you see a cutoff point where performance improves, or is it a nice (or not so nice) curve? Hazel Copied, and restored module have the same ModProps times as the original. Removing OLE diagrams didn't help. Looking inside the database I see some odd "DDn.n.dtc" files in the "Current Version" and "Baselined" versions. These few files are the about the same size as the Data files (in this case about 30mb). I haven't timed a module over time to see how general use increases the time. I notice a similar increase in time when simply displaying the "Properties" of Objects in the module. -Louie |
Re: ModuleProperties Woes Ha! It is the existance of object-level Attr-DXL which I presume is being interpreted for no good reason. Since my DXL uses include files it takes a while, it appears, to interpret. -Louie |
Re: ModuleProperties Woes llandale - Thu Feb 13 15:01:31 EST 2014 Ha! It is the existance of object-level Attr-DXL which I presume is being interpreted for no good reason. Since my DXL uses include files it takes a while, it appears, to interpret. -Louie When I hide the "addins" folders, then the ModProps time improve drastically; no doubt generating an intepret error for an unknown file is a lot faster than opening and interpreting it. |